Skip to content

[Snyk] Security upgrade @backstage/errors from 0.0.0-use.local to 0.1.1#12048

Closed
snyk-io[bot] wants to merge 1 commit intomasterfrom
snyk-fix-1ab42088d379f7e8352439903c649a2b
Closed

[Snyk] Security upgrade @backstage/errors from 0.0.0-use.local to 0.1.1#12048
snyk-io[bot] wants to merge 1 commit intomasterfrom
snyk-fix-1ab42088d379f7e8352439903c649a2b

Conversation

@snyk-io
Copy link
Copy Markdown

@snyk-io snyk-io Bot commented Feb 13, 2026

snyk-top-banner

Snyk has created this PR to fix 1 vulnerabilities in the yarn dependencies of this project.

Snyk changed the following file(s):

  • packages/repo-tools/package.json

Note for zero-installs users

If you are using the Yarn feature zero-installs that was introduced in Yarn V2, note that this PR does not update the .yarn/cache/ directory meaning this code cannot be pulled and immediately developed on as one would expect for a zero-install project - you will need to run yarn to update the contents of the ./yarn/cache directory.
If you are not using zero-install you can ignore this as your flow should likely be unchanged.

⚠️ Warning
Failed to update the yarn.lock, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

Issue Score
medium severity Allocation of Resources Without Limits or Throttling
SNYK-JS-QS-15268416
  590  

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.
  • This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic


Learn how to fix vulnerabilities with free interactive lessons:

🦉 Allocation of Resources Without Limits or Throttling


EntelligenceAI PR Summary

This PR pins the @backstage/errors dependency to version 0.1.1 in the repo-tools package, replacing the workspace protocol reference.

  • Modified dependency constraint from workspace:^ to 0.1.1 in packages/repo-tools/package.json
  • Ensures version stability by using a fixed version instead of dynamic workspace linking
  • May indicate preparation for independent package publishing outside the monorepo structure

@codesandbox
Copy link
Copy Markdown

codesandbox Bot commented Feb 13, 2026

Review or Edit in CodeSandbox

Open the branch in Web EditorVS CodeInsiders

Open Preview

@snyk-io
Copy link
Copy Markdown
Author

snyk-io Bot commented Feb 13, 2026

Snyk checks have passed. No issues have been found so far.

Status Scanner Critical High Medium Low Total (0)
Open Source Security 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

@entelligence-ai-pr-reviews
Copy link
Copy Markdown

Walkthrough

This pull request modifies the dependency management strategy for the @backstage/errors package within the repo-tools package. The change transitions from using a workspace protocol reference, which dynamically links to the local monorepo version, to a fixed version constraint (0.1.1). This modification indicates a shift towards version stability and may be part of preparation work for publishing the package independently outside the monorepo workspace structure. The pinned version ensures consistent behavior and eliminates potential issues from workspace version fluctuations.

Changes

File(s) Summary
packages/repo-tools/package.json Changed @backstage/errors dependency from workspace protocol reference (workspace:^) to fixed version 0.1.1, pinning the package to a specific version instead of using the local workspace version.

Sequence Diagram

This diagram shows the interactions between components:

sequenceDiagram
    participant PM as Package Manager
    participant RT as repo-tools Package
    participant WS as Workspace
    participant NPM as NPM Registry
    
    Note over RT: package.json updated
    Note over RT: @backstage/errors: workspace:^ → 0.1.1
    
    PM->>RT: Read package.json dependencies
    
    alt Before Change (workspace:^)
        PM->>WS: Resolve @backstage/errors from workspace
        WS-->>PM: Return local workspace version
    else After Change (0.1.1)
        PM->>NPM: Fetch @backstage/errors@0.1.1
        NPM-->>PM: Return version 0.1.1 from registry
    end
    
    PM->>RT: Install resolved dependency
    Note over RT: Now uses pinned version 0.1.1<br/>instead of workspace version
Loading

▶️AI Code Reviews for VS Code, Cursor, Windsurf
Install the extension

Note for Windsurf Please change the default marketplace provider to the following in the windsurf settings:

Marketplace Extension Gallery Service URL: https://marketplace.visualstudio.com/_apis/public/gallery

Marketplace Gallery Item URL: https://marketplace.visualstudio.com/items

Entelligence.ai can learn from your feedback. Simply add 👍 / 👎 emojis to teach it your preferences. More shortcuts below

Emoji Descriptions:

  • ⚠️ Potential Issue - May require further investigation.
  • 🔒 Security Vulnerability - Fix to ensure system safety.
  • 💻 Code Improvement - Suggestions to enhance code quality.
  • 🔨 Refactor Suggestion - Recommendations for restructuring code.
  • ℹ️ Others - General comments and information.

Interact with the Bot:

  • Send a message or request using the format:
    @entelligenceai + *your message*
Example: @entelligenceai Can you suggest improvements for this code?
  • Help the Bot learn by providing feedback on its responses.
    @entelligenceai + *feedback*
Example: @entelligenceai Do not comment on `save_auth` function !

Also you can trigger various commands with the bot by doing
@entelligenceai command

The current supported commands are

  1. config - shows the current config
  2. retrigger_review - retriggers the review

More commands to be added soon.

@github-actions
Copy link
Copy Markdown

This PR has been automatically marked as stale because it has not had recent activity from the author. It will be closed if no further activity occurs. If the PR was closed and you want it re-opened, let us know and we'll re-open the PR so that you can continue the contribution!

@github-actions github-actions Bot added the stale label Feb 20, 2026
@github-actions github-actions Bot closed this Mar 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants